| Package | hl7.ehrs.uv.phrsfmr2 |
| Type | Requirements |
| Id | Id |
| FHIR Version | R5 |
| Source | http://hl7.org/ehrs/uv/phrsfmr2/https://build.fhir.org/ig/HL7/phrsfm-ig/Requirements-PHRSFMR2-PH.3.5.5.html |
| Url | http://hl7.org/ehrs/uv/phrsfmr2/Requirements/PHRSFMR2-PH.3.5.5 |
| Version | 2.0.1-ballot |
| Status | active |
| Date | 2025-04-03T15:15:30+00:00 |
| Name | PH_3_5_5_Manage_Health_Alerts |
| Title | PH.3.5.5 Manage Health Alerts (Function) |
| Experimental | False |
| Authority | hl7 |
| Description | Notify the PHR Account Holder of an event or situation that may need immediate action. |
| Purpose | Alerts may be generated by processes both internal to the PHR-S and external from outside sources such as a provider or governmental authority. Alerts may be issued in real time or may be used after an event is past due, when a situation may require a response. Alerts are also used to notify of potentially dangerous situations such as drug interaction alerts or public health alerts. Example(s): Notify the Account Holder with alerts to a public health emergency situation. |
No resources found
No resources found
Note: links and images are rebased to the (stated) source
Notify the PHR Account Holder of an event or situation that may need immediate action.
Alerts may be generated by processes both internal to the PHR-S and external from outside sources such as a provider or governmental authority. Alerts may be issued in real time or may be used after an event is past due, when a situation may require a response. Alerts are also used to notify of potentially dangerous situations such as drug interaction alerts or public health alerts.
Example(s): Notify the Account Holder with alerts to a public health emergency situation.
| PH.3.5.5#01 | SHOULD |
The system SHOULD track alerts. |
| PH.3.5.5#02 | MAY |
The system MAY provide the ability to manage the PHR Account Holder’s response(s) to alerts. |
| PH.3.5.5#03 | MAY |
The system MAY provide the ability to manage the PHR Account Holder’s reason(s) for overriding an alert. |
| PH.3.5.5#04 | MAY |
The system MAY provide the ability to transmit to the sender of an alert the PHR Account Holder's response to that alert. |
| PH.3.5.5#05 | SHOULD |
The system SHOULD provide the ability to track PHR Account Holder -configured alerts. |
| PH.3.5.5#06 | SHOULD |
The system SHOULD provide the ability to manage PHR Account Holder alerts based on configuration parameters. |
| PH.3.5.5#07 | SHOULD |
The system SHOULD present a number of options for the PHR Account Holder to configure how they prefer to receive alerts including posting on the PHR summary screen, as well as e-mail or text messages to another e-mail account or device. |
| PH.3.5.5#08 | SHOULD |
The system SHOULD provide the ability to update content of alerts and associated reference materials. |
| PH.3.5.5#09 | SHOULD |
The system SHOULD provide the ability to receive and update alerts from PHR Account Holder’s provider(s). |
| PH.3.5.5#10 | MAY |
The system MAY provide the ability to manage the lifecycle of the states of the alerts. |
| PH.3.5.5#11 | SHOULD |
The system SHOULD provide the ability to update the established criteria that trigger the alerts. |
| PH.3.5.5#12 | conditional SHALL |
IF indications for specific preventive services and accompanying alerts were previously captured, THEN the system SHALL present alerts to the PHR Account Holder of all specific preventive services that are due. |
| PH.3.5.5#13 | MAY |
The system MAY provide the ability to render a list of all preventive services and the recommended timeframes that are due based on care plans that have been received or that exist within the PHR-S (e.g., some care plans may be imported from various care providers, another care plan may be self-generated by the PHR Account Holder). |
| PH.3.5.5#14 | MAY |
The system MAY provide the ability for the PHR Account Holder to maintain the severity level(s) for alerts (e.g., high, medium, or low priority alerts). For example, an internal clinical decision support algorithm may offer an alert to the PHR Account Holder that his blood pressure has exceeded the recommended range for his age and sex; another example is that the PHR Account Holder receives an alert from the PHR Account Holder's pharmacy's system that a medication needs to be refilled or that an existing prescription is about to expire. The PHR Account Holder could also choose to temporarily disable the presentation of low priority alerts while on vacation. |
| PH.3.5.5#15 | conditional SHOULD |
IF the PHR Account Holder changes the severity level of an alert, THEN the system SHOULD provide the ability to transmit a notice to a member of the PHR Account Holder's care team informing them that the PHR Account Holder has changed the severity level of an alert. NOTE: This transaction could be a reimbursable care-provision event for the care team member. Also, a PHR Account Holder who abides by the recommendations offered by health care alerts could be rewarded with lower premium payments (due to decreased risk of non-compliance). |
FHIR{
"resourceType" : "Requirements",
"id" : "PHRSFMR2-PH.3.5.5",
"meta" : {
"profile" : [
"http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/FMFunction"
]
},
"text" : {
"status" : "extensions",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n <span id=\"description\"><b>Statement <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b> <div><p>Notify the PHR Account Holder of an event or situation that may need immediate action.</p>\n</div></span>\n\n \n <span id=\"purpose\"><b>Description <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Informative Content\" class=\"informative-flag\">I</a>:</b> <div><p>Alerts may be generated by processes both internal to the PHR-S and external from outside sources such as a provider or governmental authority. Alerts may be issued in real time or may be used after an event is past due, when a situation may require a response. Alerts are also used to notify of potentially dangerous situations such as drug interaction alerts or public health alerts.</p>\n<p>Example(s): Notify the Account Holder with alerts to a public health emergency situation.</p>\n</div></span>\n \n\n \n <span id=\"actors\"><b>Actors:</b><br/> ehr</span>\n \n\n \n <span id=\"requirements\"><b>Criteria <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b></span>\n \n <table id=\"statements\" class=\"grid dict\">\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.3.5.5#01</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD track alerts.</p>\n</div></span>\n \n \n Satisfied by:<ol>\n \n <li><a href=\"https://www.hl7.org/fhir/communication.html\">https://www.hl7.org/fhir/communication.html</a></li>\n \n </ol>\n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.3.5.5#02</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability to manage the PHR Account Holder’s response(s) to alerts.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.3.5.5#03</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability to manage the PHR Account Holder’s reason(s) for overriding an alert.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.3.5.5#04</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability to transmit to the sender of an alert the PHR Account Holder's response to that alert.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.3.5.5#05</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to track PHR Account Holder -configured alerts.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.3.5.5#06</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to manage PHR Account Holder alerts based on configuration parameters.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.3.5.5#07</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD present a number of options for the PHR Account Holder to configure how they prefer to receive alerts including posting on the PHR summary screen, as well as e-mail or text messages to another e-mail account or device.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.3.5.5#08</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to update content of alerts and associated reference materials.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.3.5.5#09</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to receive and update alerts from PHR Account Holder’s provider(s).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.3.5.5#10</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability to manage the lifecycle of the states of the alerts.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.3.5.5#11</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to update the established criteria that trigger the alerts.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.3.5.5#12</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n <i>conditional</i>\n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>IF indications for specific preventive services and accompanying alerts were previously captured, THEN the system SHALL present alerts to the PHR Account Holder of all specific preventive services that are due.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.3.5.5#13</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability to render a list of all preventive services and the recommended timeframes that are due based on care plans that have been received or that exist within the PHR-S (e.g., some care plans may be imported from various care providers, another care plan may be self-generated by the PHR Account Holder).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.3.5.5#14</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability for the PHR Account Holder to maintain the severity level(s) for alerts (e.g., high, medium, or low priority alerts). For example, an internal clinical decision support algorithm may offer an alert to the PHR Account Holder that his blood pressure has exceeded the recommended range for his age and sex; another example is that the PHR Account Holder receives an alert from the PHR Account Holder's pharmacy's system that a medication needs to be refilled or that an existing prescription is about to expire. The PHR Account Holder could also choose to temporarily disable the presentation of low priority alerts while on vacation.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.3.5.5#15</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n <i>conditional</i>\n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>IF the PHR Account Holder changes the severity level of an alert, THEN the system SHOULD provide the ability to transmit a notice to a member of the PHR Account Holder's care team informing them that the PHR Account Holder has changed the severity level of an alert. NOTE: This transaction could be a reimbursable care-provision event for the care team member. Also, a PHR Account Holder who abides by the recommendations offered by health care alerts could be rewarded with lower premium payments (due to decreased risk of non-compliance).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n </table>\n</div>"
},
"extension" : [
{
"url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
"valueCode" : "ehr"
}
],
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/Requirements/PHRSFMR2-PH.3.5.5",
"version" : "2.0.1-ballot",
"name" : "PH_3_5_5_Manage_Health_Alerts",
"title" : "PH.3.5.5 Manage Health Alerts (Function)",
"status" : "active",
"date" : "2025-04-03T15:15:30+00:00",
"publisher" : "EHR WG",
"contact" : [
{
"telecom" : [
{
"system" : "url",
"value" : "http://www.hl7.org/Special/committees/ehr"
}
]
}
],
"description" : "Notify the PHR Account Holder of an event or situation that may need immediate action.",
"purpose" : "Alerts may be generated by processes both internal to the PHR-S and external from outside sources such as a provider or governmental authority. Alerts may be issued in real time or may be used after an event is past due, when a situation may require a response. Alerts are also used to notify of potentially dangerous situations such as drug interaction alerts or public health alerts. \r\n\r\nExample(s): Notify the Account Holder with alerts to a public health emergency situation.",
"statement" : [
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.3.5.5-01",
"label" : "PH.3.5.5#01",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD track alerts.",
"satisfiedBy" : [
"https://www.hl7.org/fhir/communication.html"
]
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.3.5.5-02",
"label" : "PH.3.5.5#02",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY provide the ability to manage the PHR Account Holder’s response(s) to alerts."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.3.5.5-03",
"label" : "PH.3.5.5#03",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY provide the ability to manage the PHR Account Holder’s reason(s) for overriding an alert."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.3.5.5-04",
"label" : "PH.3.5.5#04",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY provide the ability to transmit to the sender of an alert the PHR Account Holder's response to that alert."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.3.5.5-05",
"label" : "PH.3.5.5#05",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to track PHR Account Holder -configured alerts."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.3.5.5-06",
"label" : "PH.3.5.5#06",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to manage PHR Account Holder alerts based on configuration parameters."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.3.5.5-07",
"label" : "PH.3.5.5#07",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD present a number of options for the PHR Account Holder to configure how they prefer to receive alerts including posting on the PHR summary screen, as well as e-mail or text messages to another e-mail account or device."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.3.5.5-08",
"label" : "PH.3.5.5#08",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to update content of alerts and associated reference materials."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.3.5.5-09",
"label" : "PH.3.5.5#09",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to receive and update alerts from PHR Account Holder’s provider(s)."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.3.5.5-10",
"label" : "PH.3.5.5#10",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY provide the ability to manage the lifecycle of the states of the alerts."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.3.5.5-11",
"label" : "PH.3.5.5#11",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to update the established criteria that trigger the alerts."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.3.5.5-12",
"label" : "PH.3.5.5#12",
"conformance" : [
"SHALL"
],
"conditionality" : true,
"requirement" : "IF indications for specific preventive services and accompanying alerts were previously captured, THEN the system SHALL present alerts to the PHR Account Holder of all specific preventive services that are due."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.3.5.5-13",
"label" : "PH.3.5.5#13",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY provide the ability to render a list of all preventive services and the recommended timeframes that are due based on care plans that have been received or that exist within the PHR-S (e.g., some care plans may be imported from various care providers, another care plan may be self-generated by the PHR Account Holder)."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.3.5.5-14",
"label" : "PH.3.5.5#14",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY provide the ability for the PHR Account Holder to maintain the severity level(s) for alerts (e.g., high, medium, or low priority alerts). For example, an internal clinical decision support algorithm may offer an alert to the PHR Account Holder that his blood pressure has exceeded the recommended range for his age and sex; another example is that the PHR Account Holder receives an alert from the PHR Account Holder's pharmacy's system that a medication needs to be refilled or that an existing prescription is about to expire. The PHR Account Holder could also choose to temporarily disable the presentation of low priority alerts while on vacation."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.3.5.5-15",
"label" : "PH.3.5.5#15",
"conformance" : [
"SHOULD"
],
"conditionality" : true,
"requirement" : "IF the PHR Account Holder changes the severity level of an alert, THEN the system SHOULD provide the ability to transmit a notice to a member of the PHR Account Holder's care team informing them that the PHR Account Holder has changed the severity level of an alert. NOTE: This transaction could be a reimbursable care-provision event for the care team member. Also, a PHR Account Holder who abides by the recommendations offered by health care alerts could be rewarded with lower premium payments (due to decreased risk of non-compliance)."
}
]
}
XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.